FEND Capstone - Travel App

Architecture

The project should have a structure like the one shown below. All files shown must be present (Webpack may be split into multiple config files, and names may differ) and the app must successfully render a home page with clear design and functionality added when index.html is loaded in the browser. No errors should display in console.

- Root:
  - `package.json`
  - `readme.md`
  - `webpack.config.js`
  - src folder
    - server folder
      - `server.js` (name will vary)
    - client folder
      - `index.js`
      - html/views folder
        - `index.html`
      - js folder
        - `app.js` (name will vary)
      - styles folder
        - `style.scss` (name will vary - may be broke into partials)

Webpack

Webpack config should contain at least 3 scripts, express server, build and test. Additionally, dev server may be included.

Testing

There should be at least one test for the express server and application javascript

Offline capabilities

The project must have service workers installed.

Usability

All features are usable across modern desktop, tablet, and phone browsers.

Styling

Styling is set up in a logical way. All interactive elements have hover states.

HTML Structure

HTML structure should be indented properly with classes and ID’s that make sense.

Visual Design

The design should clearly be different from the design used in projects 3 and 4.

Server

src > server > server.js

Server should be a near duplication of project 3 with the exception of additional added member: value pairs.

index.js

src > client > index.js

• At least one function should be imported.
• At least one event listener should be imported.
• (styles referenced in html/css)

app.js

src > client > js > app.js

1. There should be URLS and API Keys for at least 3 APIs, including Geonames, Dark Sky, and Pixabay. You can feel free to use more than 3 APIs.
2. There should be a primary object with placeholder member value pairs.
3. There should be a primary function that is exported to index.js.

Extend Options / Ways to Stand Out

At least one option from the Extend your Project/Ways to Stand Out sections have been added. Please add a Note to your reviewer which one you chose to implement, or add into your README.

README

A README file is included detailing the app and all dependencies.

Other requirements:
The Readme file should have non-default text in it that is specific to this project. It doesn’t have to be thorough, but should have some basic info. Bonus points if correct markdown is used.

Comments

Comments are present and effectively explain longer code procedure when necessary.

Code Quality

Code is formatted with consistent, logical, and easy-to-read formatting as described in the Udacity JavaScript Style Guide.